Thanks for letting me know. I've just mailed the FM master asking for a value used in a certain server setting, advising him to change the value. Airio allows admins to specify message verbosity (no/set/all) on each connect, but it really would not be a good idea to force All Messages constantly to everyone. Hopefully we'll clear and correct the matter soon...
Arggghh, fail... 
Please use CheckIdling=false for now in SRV file, that should be a temporary solution, I'll look into this a bit later... Eh...
EDIT: I corrected the omission and uploaded new 2.3.3 version to the Airio site. I will wait maybe for one more day and then send update also to Franky of 500servers, probably as Airio 2.3.3 Update 1...
Please use CheckIdling=false for now in SRV file, that should be a temporary solution, I'll look into this a bit later... Eh...EDIT: I corrected the omission and uploaded new 2.3.3 version to the Airio site. I will wait maybe for one more day and then send update also to Franky of 500servers, probably as Airio 2.3.3 Update 1...
Last edited by EQ Worry, .
Well, althought it does not directly influence function of the system, I consider it as a not-quite-small bug. It is corrected now, no logs in FREE version should be lost anymore. All corrected bugs are included in the latest 2.3.3 release available on the download page. And thanks for such reports - you experience something strange, just let me know. Correction usually is not complicated, sometimes discovering the issue is the hardest part.
Hi Highway and thanks for the reports. The first one is actually some kind of bug. Even after detailed check of the code I'm still not sure how it could happen. But to be sure it doesn't repeat I added there range conditions.
The 2nd one is intended behavior. I added these messages to fight some clicked button issues appearing sporadically. For now they're always stored, I'll remove them soon. The strange thing is why there is 13 clicks on the same button within 2 seconds... Hmmm... Maybe holding down the button? Must check...
The 2nd one is intended behavior. I added these messages to fight some clicked button issues appearing sporadically. For now they're always stored, I'll remove them soon. The strange thing is why there is 13 clicks on the same button within 2 seconds... Hmmm... Maybe holding down the button? Must check...
Haha, pity you didn't mention that one, it could have been solved for days already.
Eh, people can be very inventive when searching for some kind of advantage for themselves.
Well, I guess it would be possible to prevent car type switching when pitting after sorting the grid. I'll look into this and try to come up with some simple solution soon.Aaah, good one! Thanks! It is indeed a bug, not very serious, but still a bug. Fortunately easy to solve, I'll be updating the FREE version in a few minutes, FULL version a bit later tonight.
Generally Airio catches all internal errors, stores them into its log and continues in processing. But there should be NO errors reported, so I'm grateful for reporting all such ocurrences - best way is just as VoiD did, together with pertinent part of the Airio log.
Ah, just a while ago I discovered a serious bug in the ASP.NET code gathering and displaying global Airio usage stats. It is corrected now and I believe this will significantly improve the servers page availability...
I hope this is good news for jvalley and others: Airio 2.3.3 is released, because no bug reports from testers were coming for some days now. This update is already sent to Franky of 500servers, hopefully it will be available soon. EDIT: It is already, good work!
The final version reverts some additions from beta 2 and beta 3. It removes from Airio host info reading using LFSW. On second thought it is much more logical to read the data just once a minute on the Airio website and apply them on server page. Also the CFG option to hide hidden servers is removed, servers not found on LFSW list are now always marked as hidden, no configuraton necessary.
The final version reverts some additions from beta 2 and beta 3. It removes from Airio host info reading using LFSW. On second thought it is much more logical to read the data just once a minute on the Airio website and apply them on server page. Also the CFG option to hide hidden servers is removed, servers not found on LFSW list are now always marked as hidden, no configuraton necessary.
Last edited by EQ Worry, .
Hm, interesting idea. But you should realize the system log is sort of internal file very handy for discovering bugs and also for admins to see in retrospect different actions of some drivers. Into the file various server events and Airio actions are recorded. While there is a general structure to info presented (see below), I'm basically sending there what I consider of general interest and also what is necessary for some debugging. This means the items can change - not by much, sure, but there may be changes over time, although mostly new additions. All items have this format:
[I]server_date[/I] [I]server_time[/I] #[I]server_number[/I] [B]C[/B][I]connection_id[/I][B]P[/B][I]player_id[/I] [I]username[/I] [I]description[/I]On some lines the C, P, and name is not applicable, so it is not stored. Some other lines omit even server number, because they apply to whole instance. I believe the descriptions are short but sufficient, anyone interested in the system log should not have troubles reading it and understanding the sequence of events. It gives nice insight. Hope this helps.
Very right in all respects.
On dedicated servers the host is connection 0 and player 0.On another note, Airio 2.3.3 beta 3 is available solving some issues with LFSW host data used on Airio servers page and also adding BName item into CFG files allowing to define permanently banned usernames. This list may be made external using IncludeFile option.
Last edited by EQ Worry, .
1) If it is about speeds, then the problem is somewhere else. You can see Beste Runde (best lap) 1:33:95 (yellow time) somewhere in the middle, and then below Schnellste Runde (fastest lap) twice, once as 1:45.47 and once as 1:33:99 (time is gray). The thing is the two other messages are not generated by Airio, they come from LFS itself. Only the first one, with yellow time, comes from Airio.
LFS handles best times differently, it considers only cars that are currently on track. Airio keeps just one value for the whole race, regardless of on track/on server state of that driver. So SirErich made the real best lap an then pitted (geth an die Box). From that moment LFS ignores his lap time, showing (incorrectly, i my opinion) two new best lap times. I cannot do anything about it, the best solution may be if LFS developer allowed to turn off best lap reporting by the engine.
2) Other potential confusion may be the car types. Airio shows FX2 with SirErich, while the results table mentiones FXR. FX2 is of course custom-defined car with some restrictions (say intake air by 24 percent). Any FXR seen with that or higher restrictions is handled in Airio separately as a special new type. It can be part of some car category (say GT2) and it has completely separate stats called e.g. by !sb fx2 or !pb fx2.
Of course LFS itself knows nothing about custom cars, so in its output (such as the results table) it will show car type as FXR. To see correct used car types also separated into car categories, type !results or just !rs. The output shows sorted results by categories with total race time, time lost to previous driver, points for the race and in series and other info.
LFS handles best times differently, it considers only cars that are currently on track. Airio keeps just one value for the whole race, regardless of on track/on server state of that driver. So SirErich made the real best lap an then pitted (geth an die Box). From that moment LFS ignores his lap time, showing (incorrectly, i my opinion) two new best lap times. I cannot do anything about it, the best solution may be if LFS developer allowed to turn off best lap reporting by the engine.
2) Other potential confusion may be the car types. Airio shows FX2 with SirErich, while the results table mentiones FXR. FX2 is of course custom-defined car with some restrictions (say intake air by 24 percent). Any FXR seen with that or higher restrictions is handled in Airio separately as a special new type. It can be part of some car category (say GT2) and it has completely separate stats called e.g. by !sb fx2 or !pb fx2.
Of course LFS itself knows nothing about custom cars, so in its output (such as the results table) it will show car type as FXR. To see correct used car types also separated into car categories, type !results or just !rs. The output shows sorted results by categories with total race time, time lost to previous driver, points for the race and in series and other info.
Hm, I'm sorry but I can't see a problem there. Can you please elaborate as to what seems strange/incorrect to you?
EDIT: Airio 2.3.3 beta 2 is available, adding 2 new personalization options and allowing to "hide hidden servers", just as using additional state data from LFSW host lists.
EDIT: Airio 2.3.3 beta 2 is available, adding 2 new personalization options and allowing to "hide hidden servers", just as using additional state data from LFSW host lists.
Last edited by EQ Worry, .
Understood, but it is something nobody can help you with, except the cooperation of the two main LFS developers. And seeing how things move forward recently and the principles applied, frankly, I doubt it will ever be implemented.
Airio 2.3.3 is now released. Due to many new features and improvements some things need to be tested more thoroughly than I'm able to do, so it has currently status of Beta 1. As mentioned, it brings many smaller and larger things that I wanted (or was asked) to implement, so the changelog is rather long. But here's a few picks that may be of some general interest:
- Instead of Shift+i the personal config may be also called by !opt command.
- There is a few parameters that can be used in custom texts, but generally speaking creating many parameters is not the way I want to go.
- FULL version implements very useful custom user commands just as several internal options of selecting a driver and sending him some text into chat or buttons, optionally for certain amount of time.
- FREE version can connect to any number of servers at once, it is not limited to 4 anymore.
- Yellow flag check (and some others) were improved by introducing the principle of "near" cars, that would reach your position in a certain configurable time. If there isn't anyone near you, yellow flag, spinning and lagging checks are ignored.
- It is now possible (though not recommended) to enforce/prohibit automatic clutch and shifter, if you want a server only for those with best equipment.
- In FULL compile any LFS/Airio commands can be specified in rotation, making it much more flexible. Pit windows can also be defined by (leader) laps and not just by (race) minutes.
- Using defined race path simple proper pitlane entry/exit checks may be implemented on some tracks (BL1, KY1) with definable penalties (applied only in race).
- People may see their position in any sorted list by using # instead of [from] parameter. That means !sb # is equivalent to !near, but you may also use e.g. !champ #, !races #, and many other similar commands.
- Champ/total stats commands now also accept multiple cars, meaning !races tbo or !drift BL2+XFG+XRG are perfectly valid requests.
- Many other things were corrected or improved.
Thanks as well...
Makes me wonder what that serious reason is
, but this is a valid note. Earlier Airio versions actually had a "hidden" option, but I later removed it. First, I didn't want any FULL versions run hidden, second, all the data are visible anyway on the LFSW site, so it's nothing secret.But your note is valid. Best option I see is checking if the LFS server is hidden and then also auto-hide that Airio data on the servers page. But currently I do not see an easy way how to do this. Maybe through LFSW request/response to check existence of the server, but this would require some research and experiments first. But I'll try to offer some solution, not in upcoming 2.3.3 though.
Prohibiting certain tag (specific part of nickname) use on your server with Airio is rather easy, but it has limitations. The impostors will not be ale to use the tag on your server, but they'll be free to do so on any other server.
To have your team tag protected also on other team servers running under Airio you'd need to agree with the admins there to define your tag as prohibited name and to include all your real team members as Limad0 into configuration. Limads 0 by default have no additional rights except the possibility to use prohibited names. (But to be sure check the Allowed Limad Actions section in CFG file.)
To have your team tag protected also on other team servers running under Airio you'd need to agree with the admins there to define your tag as prohibited name and to include all your real team members as Limad0 into configuration. Limads 0 by default have no additional rights except the possibility to use prohibited names. (But to be sure check the Allowed Limad Actions section in CFG file.)
If there are "strange" spectatings, it is best to check the Airio LOG file, where every action is stored including the reason.
For any serious (planned, endurance) racing I always suggest to turn off some of the checks, because you really do not want people kicked for inactivity (which is for demo with limited number of slots anyway), spectated for fast driving in pits and for many other things (crashing, idling).
Airio versions prior to 2.3.0 had a single commad for turning all checks: !ch off. Type it and Airio will never spectate/kick anyone, yet it will (optionally) display and keep all timing data.
Airio 2.3.0 and newer have the filters separated into two categories that can be turned on/off separately. Basic checks are in fact joining checks enforcing time lock, restrictions and such things. They can be turned off by !chb off, but this really isn't necessary.
For serious racing you'd want to turn off the advanced checks by !cha off. You'll get to a mode enforcing all joining limitations (e.g. rank/licence required), but basically ignoring cars once they're on track.
To summarize: It is not necessary to turn off Airio completely, you may turn off just selected checks or simply turn off all advanced checks at once and there'll be no forced spectatings.
Hope this helps.
For any serious (planned, endurance) racing I always suggest to turn off some of the checks, because you really do not want people kicked for inactivity (which is for demo with limited number of slots anyway), spectated for fast driving in pits and for many other things (crashing, idling).
Airio versions prior to 2.3.0 had a single commad for turning all checks: !ch off. Type it and Airio will never spectate/kick anyone, yet it will (optionally) display and keep all timing data.
Airio 2.3.0 and newer have the filters separated into two categories that can be turned on/off separately. Basic checks are in fact joining checks enforcing time lock, restrictions and such things. They can be turned off by !chb off, but this really isn't necessary.
For serious racing you'd want to turn off the advanced checks by !cha off. You'll get to a mode enforcing all joining limitations (e.g. rank/licence required), but basically ignoring cars once they're on track.
To summarize: It is not necessary to turn off Airio completely, you may turn off just selected checks or simply turn off all advanced checks at once and there'll be no forced spectatings.
Hope this helps.
Yes, they run Remote+ there and you were penalized by this service. I myself do not like the + version much, there are other means to fight deliberate cutting.
AFAIK this isn't Airio again, it is a standard LFS restricted zone (layout) defined there by FM people, easy to update if it affects your racing line. Airio by default contains only two anti-crasher restricted (spec) zones defined on BL1 and one limited (lap stats not saved) on BL2 for the demo configs, everything else is open. There may be a race path check running invalidating server PBs if achieved by cutting, but Airio usually does not spec/pen people for cutting.
First thing to know is that again it is an admin-optional check, disabled by default. Second point is it can be configured only for specific tracks, such as SO. I agree that on WE and other wide tracks it is rather useless/frustrating.
But your idea about making sure some of the checks (yellow flag, safety spectating) are not applied if there's no one close around is really cool, I'll add this into final Airio 2.3.3, so that the "true spawn of the satan" is less devilish. But, as you can read above, not all evil comes from Airio.
BIG SORRY to everyone for this highly off-topic discussion. I just stumbled across a complaint concerning my tool and I wanted to learn a bit more about the cause and possible solutions.
The answer is of course simple - there are a lot of people and everyone considers as garbage something different. Someone really doesn't want to see anything, racing in Shift+F mode, so he can turn off everything. Some don't care about ranks/licences, so they choose to ignore that data. Admins certainly want to see spectate/kick reasons, while others may ignore such messages. Maybe, just maybe, all these possibilities are one of the reasons why the FOX server is busy.
Yes, that is valid objection, and the (optional) message is there for 2 reasons: One is there are differences - LFS doesn't say what car was it, which may be important, and LFS also considers only cars on track. The other is simply to have things complete, artificially skipping that info does not feel right to me.
Yes, this message is the most hated and I'll be updating the code to fight it a bit. But again, it has a purpose - it tells you your safety rating went down a bit (while completing laps and races raise it). Problem is LFS gives you yellow flag even when you are alone on server (sic), so I'll need to add a few more checks to see if it has meaning.
Well, that is quite up to server administrators to decide. By default Airio doen't run bad language check, if it is active it means it was turned on intentionally by admins.
Hm, I'm not sure what you mean, because Airio doesn't give any penalties for cutting, just for the reason you mention, it simply may be necessary. AAAH, I know! It was the Remote+ that gave you the penalty - one warning, then penalty, right? Nothing to do with Airio, it is Victor's work - ask admins to run simple Remote (not the plus version).
Stop there? What would be the point? Why blame me or Airio for giving every driver tens of configuration options (with a very low-profile initial settings) and a hundred+ options to server admins, again most of them inactive by default? If you're not happy with some spectate/kick reasons, ask admins to change the settings. Would you complain to LFS developers because on some servers there is forced cockpit view? I doubt. You would ask admins for change or simply leave.
Right, I apologise, it was just to mention the primary topic of this thread. So I will elaborate a bit now: Yes, wi-fi may add on average negligible 1 or 2 ms, but the problem is the communication is easy to break through interference (turn on a light, car passes nearby, whatever), and then it takes hundreds of miliseconds to reestablish/repeat the what was lost. That is why, in my opinion, wi-fi is not a good choice for online action/sim gaming. And anyone using wi-fi (as I do sometimes) should be aware of this.
Info about auto clutch (just as about shifter or controls used - kb, mouse, wheel) is part of standard InSim data available e.g. when player enters the track. It is actually quite simple to add this check into Airio with two configurable options: One to prohibit auto clutch, the other to require it.
I'm not sure what was the result of the whole discussion, but I guess just having the mentioned two options (to keep things ballanced) should not hurt anybody. Cars joining with disallowed clutch settings will be spectated (with appropriate explanation) for bad setup and that's it. By default any setting will be allowed...
EDIT: Done, auto clutch and shifter may be required or disallowed in Airio 2.3.3, to be released in one or two days. Any server admin should know however these could be highly restrictive options that must be used with care.
I'm not sure what was the result of the whole discussion, but I guess just having the mentioned two options (to keep things ballanced) should not hurt anybody. Cars joining with disallowed clutch settings will be spectated (with appropriate explanation) for bad setup and that's it. By default any setting will be allowed...
EDIT: Done, auto clutch and shifter may be required or disallowed in Airio 2.3.3, to be released in one or two days. Any server admin should know however these could be highly restrictive options that must be used with care.
Last edited by EQ Worry, .
If Airio reports you as lagging, it really means you are lagging. The measurement is very objective, server data are used for that. Server reports it misses your car position and if there's several such ocurrences in a row and they repeat again and again, then you're noticed, later spectated.
If server misses your car position, then naturally everyone else driving misses that position as well. Server supplies artificial position of your car (based on previous movement) to everyone, correcting it when new data arrive, that's why the car is jumping. An jumping cars are dangerous.
Also I'm not sure why you'd call Airio a "true spawn of satan". Too many messages, too much spamming? Turn off for yourself anything you do not need (try the magic Shift+i, maybe twice)! It is about the only InSim that may run completely silently for you (try !silent in latest versions), showing only a few really important messages, such as why you were spectated.
If you're not happy with the lagging check or spinning check or something else, then you should ask admins to change the settings or turn off the appropriate filter. If they are not willing to go that way, certainly it is not Airio's fault.
And yes, using wi-fi leads to lagging.
Just a very small note: Newer Airio (something like 2.3.2+) counts objects (cones) hit and adds the (number * 2 seconds) to every split/sector/lap time, so that all the !sb and !pb data include the penalties. You can check this in action at [AKM] Airio Dev server with a tricky FE4 layout.
Very valid note, thanks, man! Grid clearing was until now really happening only when changing tracks, which was not correct. Airio 2.3.3 (to be released soon) clears the grid on every race end, which should solve your troubles.
Just to be sure it is understood: The DLL files did not change for a loooong time, so I believe you just need to ask the admins there to upload them once and it is done, the standard updates you can do yourself...
so I believe you just need to ask the admins there to upload them once and it is done, the standard updates you can do yourself...I have no experience with Storm servers. If they install Airio for you to be controlled by some panel and you have the option to overwrite EXE (and DLL) files, then you're the master and you can upgrade/update yourself.
Without EXE overwrite rights it may get more complicated - you either need to always ask the management to update it for you or you need an auto-update service, but that would require some arrangement between me and them, similar to what I have with 500servers owner (sending him mails with updates, which are then available).
In SRV file there are 2 items setting rotation. Example:
RotateRaces=8
RotateTracks=BL1|5|FBM > BL1|4|XFG+XRG > BL2|5|XFG+XRGWith these settings rotation will start when 8 races are finished OR race end screen is shown (either by voting to end race or when last driver leaves the server). I believe the parameters used are rather obvious (track, laps, cars).
FGED GREDG RDFGDR GSFDG